build: update dependency yargs to v18 - autoclosed #2838

angular-robot · 2025-05-28T05:10:06Z

This PR contains the following updates:

Package	Type	Update	Change
yargs (source)	dependencies	major	`^17.0.0` -> `^18.0.0`
yargs (source)	dependencies	major	`17.7.2` -> `18.0.0`

Release Notes

yargs/yargs (yargs)

`v18.0.0`

Compare Source

⚠ BREAKING CHANGES

command names are not derived from modules passed to command.
singleton usage of yargs yargs.foo, yargs().argv, has been removed.
minimum node.js versions now ^20.19.0 || ^22.12.0 || >=23.
yargs is now ESM first

Features

commandDir now works with ESM files (#2461) (27eec18)
locale: adds hebrew translation (#2357) (4266485)
yargs is now ESM first (d90af45)
zsh: Add default completion as fallback (#2331) (e02c91b)

Bug Fixes

addDirectory do not support absolute command dir (#2465) (3a40a78)
allows ESM modules commands to be extensible using visit option (#2468) (200e1aa)
browser: fix shims so that yargs continues working in browser context (#2457) (4ae5f57)
build: address problems with typescript compilation (#2445) (8d72fb3)
coerce should play well with parser configuration (#2308) (8343c66)
deps: update dependency yargs-parser to v22 (#2470) (639130d)
exit after async handler done (#2313) (e326cde)
handle spaces in bash completion (#2452) (83b7788)
parser-configuration should work well with generated completion script (#2332) (888db19)
propagate Dictionary including undefined in value type (#2393) (2b2f7f5)
zsh: completion no longer requires double tab when using autoloaded (0dd8fe4)

Code Refactoring

command names are not derived from modules passed to command. (d90af45)
singleton usage of yargs yargs.foo, yargs().argv, has been removed. (d90af45)

Build System

minimum node.js versions now ^20.19.0 || ^22.12.0 || >=23. (d90af45)

Configuration

📅 Schedule: Branch creation - "after 10:00pm every weekday,before 5:00am every weekday,every weekend" in timezone America/Tijuana, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

See associated pull request for more information.

angular-robot · 2025-05-28T05:10:07Z

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: undefined

Command failed: yarn update-generated-files
Loading: 
Loading: 
Loading: 
Loading: 
Loading: 
Loading: 
Loading: 0 packages loaded
Analyzing: target //ng-dev:npm_package (1 packages loaded, 0 targets configured)
Analyzing: target //ng-dev:npm_package (318 packages loaded, 12874 targets configured)
Analyzing: target //ng-dev:npm_package (399 packages loaded, 19621 targets configured)
INFO: Analyzed target //ng-dev:npm_package (399 packages loaded, 19626 targets configured).
INFO: Found 1 target...
[4 / 6] [Prepa] BazelWorkspaceStatusAction stable-status.txt
[141 / 219] [Sched] Compiling TypeScript (devmode) @//ng-dev/utils:g3_sync_config ... (2 actions, 0 running)
[141 / 219] Compiling TypeScript (devmode) @//ng-dev/utils:g3_sync_config; 1s worker ... (4 actions running)
[143 / 219] Compiling TypeScript (devmode) @//ng-dev/utils:g3_sync_config; 3s worker ... (2 actions running)
[145 / 219] Compiling TypeScript (prodmode) @//ng-dev/utils:utils; 0s worker ... (2 actions running)
[146 / 219] Compiling TypeScript (devmode) @//ng-dev/utils:utils; 2s worker
[147 / 219] Compiling TypeScript (prodmode) @//ng-dev/pullapprove:pullapprove; 0s worker ... (4 actions running)
[150 / 219] Compiling TypeScript (devmode) @//ng-dev/ts-circular-dependencies:ts-circular-dependencies; 2s worker ... (4 actions, 3 running)
[150 / 219] Compiling TypeScript (devmode) @//ng-dev/ts-circular-dependencies:ts-circular-dependencies; 3s worker ... (4 actions running)
[152 / 219] Compiling TypeScript (devmode) @//ng-dev/perf/workflow:workflow; 4s worker ... (4 actions running)
[154 / 219] Compiling TypeScript (devmode) @//ng-dev/perf/workflow:workflow; 5s worker ... (4 actions running)
[157 / 219] Compiling TypeScript (devmode) @//ng-dev/perf/workflow:workflow; 6s worker ... (4 actions running)
[159 / 219] Compiling TypeScript (devmode) @//ng-dev/perf/workflow:workflow; 7s worker ... (4 actions running)
[163 / 219] Compiling TypeScript (prodmode) @//ng-dev/auth:auth; 1s worker ... (4 actions running)
[165 / 219] Compiling TypeScript (prodmode) @//ng-dev/auth:auth; 2s worker ... (4 actions, 3 running)
[166 / 219] Compiling TypeScript (prodmode) @//ng-dev/auth:auth; 4s worker ... (4 actions running)
[170 / 219] Compiling TypeScript (devmode) @//ng-dev/auth:auth; 2s worker ... (4 actions running)
[173 / 219] Compiling TypeScript (devmode) @//ng-dev/release/versioning:versioning; 1s worker ... (4 actions, 3 running)
[176 / 219] Compiling TypeScript (devmode) @//ng-dev/pr/config:config; 1s worker ... (4 actions running)
[179 / 219] Compiling TypeScript (devmode) @//ng-dev/caretaker:caretaker; 1s worker ... (4 actions, 3 running)
[182 / 219] Compiling TypeScript (prodmode) @//ng-dev/release/versioning:versioning; 1s worker ... (4 actions, 3 running)
[185 / 219] Compiling TypeScript (devmode) @//ng-dev/pr/check-target-branches:check-target-branches; 1s worker ... (4 actions, 3 running)
[187 / 219] Compiling TypeScript (prodmode) @//ng-dev/release/npm-dist-tag/delete:delete; 1s worker ... (4 actions running)
[189 / 219] Compiling TypeScript (devmode) @//ng-dev/pr/checkout:checkout; 1s worker ... (4 actions running)
[192 / 219] Compiling TypeScript (devmode) @//ng-dev/pr/checkout:checkout; 2s worker ... (4 actions running)
[196 / 219] Compiling TypeScript (devmode) @//ng-dev/pr/discover-new-conflicts:discover-new-conflicts; 0s worker ... (4 actions running)
[199 / 219] Compiling TypeScript (prodmode) @//ng-dev/release/npm-dist-tag:npm-dist-tag; 1s worker ... (3 actions, 2 running)
[202 / 219] Compiling TypeScript (devmode) @//ng-dev/pr/merge:merge; 1s worker ... (4 actions, 3 running)
[204 / 219] Compiling TypeScript (prodmode) @//ng-dev/pr/merge:merge; 2s worker ... (4 actions running)
[206 / 219] Compiling TypeScript (prodmode) @//ng-dev/pr/checkout:checkout; 1s worker ... (4 actions running)
[208 / 219] Compiling TypeScript (devmode) @//ng-dev/release/publish:publish; 2s worker ... (3 actions running)
[211 / 219] Compiling TypeScript (prodmode) @//ng-dev/release/publish:publish; 2s worker ... (4 actions, 3 running)
[214 / 219] Compiling TypeScript (prodmode) @//ng-dev/pr:pr; 1s worker ... (3 actions running)
[216 / 219] Compiling TypeScript (prodmode) @//ng-dev:ng-dev; 2s worker ... (2 actions, 1 running)
ERROR: /tmp/renovate/repos/github/angular/dev-infra/ng-dev/BUILD.bazel:55:19: Splitting Javascript ng-dev/cli.ts ng-dev/index.ts ng-dev/release/build/build-worker.ts ng-dev/pr/merge/strategies/commit-message-filter.ts ng-dev/pr/checkout/commit-message-filter.ts [esbuild] failed: (Exit 1): _bundles_esbuild_launcher.sh failed: error executing command (from target //ng-dev:bundles) bazel-out/k8-opt-exec-2B5CBBC6/bin/ng-dev/_bundles_esbuild_launcher.sh '--esbuild_args=bazel-out/k8-fastbuild/bin/ng-dev/bundles.args.json' ... (remaining 2 arguments skipped)

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
✘ [ERROR] Using a string as a module namespace identifier name is not supported in the configured target environment ("node14")

    node_modules/yargs/index.mjs:10:17:
      10 │ export {Yargs as 'module.exports'};
         ╵                  ~~~~~~~~~~~~~~~~

✘ [ERROR] Using a string as a module namespace identifier name is not supported in the configured target environment ("node14")

    node_modules/yargs/node_modules/cliui/index.mjs:15:14:
      15 │ export {ui as 'module.exports'};
         ╵               ~~~~~~~~~~~~~~~~

✘ [ERROR] Using a string as a module namespace identifier name is not supported in the configured target environment ("node14")

    node_modules/yargs/node_modules/yargs-parser/build/lib/index.js:64:24:
      64 │ export { yargsParser as 'module.exports' };
         ╵                         ~~~~~~~~~~~~~~~~

Error: Build failed with 3 errors:
node_modules/yargs/index.mjs:10:17: ERROR: Using a string as a module namespace identifier name is not supported in the configured target environment ("node14")
node_modules/yargs/node_modules/cliui/index.mjs:15:14: ERROR: Using a string as a module namespace identifier name is not supported in the configured target environment ("node14")
node_modules/yargs/node_modules/yargs-parser/build/lib/index.js:64:24: ERROR: Using a string as a module namespace identifier name is not supported in the configured target environment ("node14")
    at failureErrorWithLog (/home/runner/.cache/bazel/_bazel_runner/5d5a7feccad26433ec06445e3849315a/sandbox/processwrapper-sandbox/208/execroot/devinfra/external/npm/@bazel/esbuild/node_modules/esbuild/lib/main.js:1575:15)
    at /home/runner/.cache/bazel/_bazel_runner/5d5a7feccad26433ec06445e3849315a/sandbox/processwrapper-sandbox/208/execroot/devinfra/external/npm/@bazel/esbuild/node_modules/esbuild/lib/main.js:1033:28
    at /home/runner/.cache/bazel/_bazel_runner/5d5a7feccad26433ec06445e3849315a/sandbox/processwrapper-sandbox/208/execroot/devinfra/external/npm/@bazel/esbuild/node_modules/esbuild/lib/main.js:978:67
    at buildResponseToResult (/home/runner/.cache/bazel/_bazel_runner/5d5a7feccad26433ec06445e3849315a/sandbox/processwrapper-sandbox/208/execroot/devinfra/external/npm/@bazel/esbuild/node_modules/esbuild/lib/main.js:1031:7)
    at /home/runner/.cache/bazel/_bazel_runner/5d5a7feccad26433ec06445e3849315a/sandbox/processwrapper-sandbox/208/execroot/devinfra/external/npm/@bazel/esbuild/node_modules/esbuild/lib/main.js:1143:14
    at responseCallbacks.<computed> (/home/runner/.cache/bazel/_bazel_runner/5d5a7feccad26433ec06445e3849315a/sandbox/processwrapper-sandbox/208/execroot/devinfra/external/npm/@bazel/esbuild/node_modules/esbuild/lib/main.js:680:9)
    at handleIncomingPacket (/home/runner/.cache/bazel/_bazel_runner/5d5a7feccad26433ec06445e3849315a/sandbox/processwrapper-sandbox/208/execroot/devinfra/external/npm/@bazel/esbuild/node_modules/esbuild/lib/main.js:735:9)
    at Socket.readFromStdout (/home/runner/.cache/bazel/_bazel_runner/5d5a7feccad26433ec06445e3849315a/sandbox/processwrapper-sandbox/208/execroot/devinfra/external/npm/@bazel/esbuild/node_modules/esbuild/lib/main.js:656:7)
    at Socket.emit (node:events:524:28)
    at addChunk (node:internal/streams/readable:561:12) {
  errors: [
    {
      detail: undefined,
      id: '',
      location: [Object],
      notes: [],
      pluginName: '',
      text: 'Using a string as a module namespace identifier name is not supported in the configured target environment ("node14")'
    },
    {
      detail: undefined,
      id: '',
      location: [Object],
      notes: [],
      pluginName: '',
      text: 'Using a string as a module namespace identifier name is not supported in the configured target environment ("node14")'
    },
    {
      detail: undefined,
      id: '',
      location: [Object],
      notes: [],
      pluginName: '',
      text: 'Using a string as a module namespace identifier name is not supported in the configured target environment ("node14")'
    }
  ],
  warnings: []
}
Target //ng-dev:npm_package failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 69.999s, Critical Path: 24.77s
INFO: 151 processes: 76 internal, 75 worker.
FAILED: Build did NOT complete successfully

angular-automatic-lock-bot · 2025-06-28T00:12:40Z

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}

build: update dependency yargs to v18

127bc2d

See associated pull request for more information.

angular-robot added action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project labels May 28, 2025

angular-robot changed the title ~~build: update dependency yargs to v18~~ build: update dependency yargs to v18 - autoclosed May 28, 2025

angular-robot closed this May 28, 2025

angular-robot deleted the ng-renovate/yargs-18-x branch May 28, 2025 10:10

angular-automatic-lock-bot bot locked and limited conversation to collaborators Jun 28, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

build: update dependency yargs to v18 - autoclosed #2838

build: update dependency yargs to v18 - autoclosed #2838

Uh oh!

angular-robot commented May 28, 2025

Uh oh!

angular-robot commented May 28, 2025

Uh oh!

angular-automatic-lock-bot bot commented Jun 28, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

build: update dependency yargs to v18 - autoclosed #2838

build: update dependency yargs to v18 - autoclosed #2838

Uh oh!

Conversation

angular-robot commented May 28, 2025

Release Notes

v18.0.0

⚠ BREAKING CHANGES

Features

Bug Fixes

Code Refactoring

Build System

Configuration

Uh oh!

angular-robot commented May 28, 2025

⚠️ Artifact update problem

File name: undefined

Uh oh!

angular-automatic-lock-bot bot commented Jun 28, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

`v18.0.0`